Example project — Frond is not real.

Authored demo content for a fictional plant-care app, rendered by the same parsers and held to the same invariants as a real project's dashboard. This is the system in use, three months in.

docs/planning/Future Considerations.mdWorkingactive2026-07-20Read when: at phase open (check for fired triggers) and phase close (prune shipped)

Future Considerations

Known directions waiting for a trigger. Items graduate out — to the punch list, a phase board, or feature scope — when their trigger fires.

FC7. Shared households

Trigger: a support request from two users watering the same plant, or the first paid tier discussion. Context: Two people, one plant list. Needs a real permission model and turns the digest-time question (Open Questions §3) into a genuine conflict. Big enough to be its own milestone, not a phase. Effort: large Refs: docs/planning/Open Questions & Assumptions Log.md §3 Added: 2026-06-29

FC8. Southern-hemisphere seasons

Trigger: the first user outside the northern hemisphere, or any marketing outside it. Context: Seasonal adjustment is hardcoded to one hemisphere (ROADMAP.md → Key Considerations). The fix is small and the embarrassment is not, so this graduates the moment it is real. Effort: small Refs: strategy/Care Model.md Added: 2026-07-05

FC9. Fertiliser schedules

Trigger: watering retention holds for two months, proving the habit exists to attach to. Context: Explicitly out of the first milestone. Only worth building once watering is a habit, because it rides on the same digest and would otherwise dilute it. Effort: medium Refs: strategy/Scope & Constraints.md Added: 2026-07-11